Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: support --config #38

Merged
merged 3 commits into from
Oct 17, 2022
Merged

feat: support --config #38

merged 3 commits into from
Oct 17, 2022

Conversation

kecrily
Copy link
Member

@kecrily kecrily commented Sep 29, 2022

close #23 #35

@abitrolly
Copy link

Will that solve #39?

@kecrily
Copy link
Member Author

kecrily commented Oct 7, 2022

No, but if you have an extend that you want to use, then this PR can solve it.

@abitrolly
Copy link

I don't know what the extend is. Not from JS world, just devopsing.

Copy link
Member

@aladdin-add aladdin-add left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can you also update the usage in the readme?

lib/init/config-initializer.js Outdated Show resolved Hide resolved
Copy link
Member

@aladdin-add aladdin-add left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM~

Copy link
Member

@mdjermanovic mdjermanovic left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would it be possible to add some tests for this feature now, or does that have to wait for #16?

@kecrily
Copy link
Member Author

kecrily commented Oct 16, 2022

I think we need to wait for the e2e tests to be written and then test this uniformly.

README.md Outdated
Comment on lines 24 to 27
npm init @eslint/config --config eslint
# or (`eslint-config` prefix is optional)
npm init @eslint/config --config eslint-config-eslint
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
# use `eslint-config-eslint` shared config
npm init @eslint/config --config eslint
# or (`eslint-config` prefix is optional)
npm init @eslint/config --config eslint-config-eslint
# use `eslint-config-semistandard` shared config
npm init @eslint/config --config semistandard
# or (`eslint-config` prefix is optional)
npm init @eslint/config --config eslint-config-semistandard

I think eslint-config-eslint could be confusing. It might be better to use something like semistandard for the example?

README.md Outdated
npm init @eslint/config --config eslint,standard
# or
npm init @eslint/config --config eslint --config standard
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This doesn't seem to work. I'm getting TypeError: argv.config.split is not a function because in this case argv.config is an array.

@mdjermanovic mdjermanovic linked an issue Oct 16, 2022 that may be closed by this pull request
Copy link
Member

@mdjermanovic mdjermanovic left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Can't create config with React + Typescript + Airbnb support --config
4 participants